Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Zephyr] Fix General Diagnostics Hardware Address #24941

Merged
merged 1 commit into from
Feb 9, 2023

Conversation

Damian-Nordic
Copy link
Contributor

15.4 drivers in Zephyr set EUI-64 as the link-layer address of the corresponding interface. However, Hardware Address field in the General Diagnostics cluster is supposed to return Extended Address for Thread interfaces according to the specification.

Make sure the diagnostic data provider returns the extended address for the concerned field.

15.4 drivers in Zephyr set EUI-64 as the link-layer address
of the corresponding interface. However, Hardware Address
field in the General Diagnostics cluster is supposed to
return Extended Address for Thread interfaces according to
the specification.

Make sure the diagnostic data provider returns the extended
address for the concerned field.

Signed-off-by: Damian Krolik <[email protected]>
@Damian-Nordic Damian-Nordic changed the title [nrf fromlist] [Zephyr] Fix General Diagnostics Hardware Address [Zephyr] Fix General Diagnostics Hardware Address Feb 9, 2023
@github-actions
Copy link

github-actions bot commented Feb 9, 2023

PR #24941: Size comparison from cc0f0d8 to 69b03f5

Full report (1 build for cc32xx)
platform target config section cc0f0d8 69b03f5 change % change
cc32xx lock CC3235SF_LAUNCHXL 0 0 0 0.0
(read only) 640233 640233 0 0.0
(read/write) 204084 204084 0 0.0
.ARM.attributes 44 44 0 0.0
.ARM.exidx 8 8 0 0.0
.bss 197488 197488 0 0.0
.comment 194 194 0 0.0
.data 1476 1476 0 0.0
.debug_abbrev 928439 928439 0 0.0
.debug_aranges 87352 87352 0 0.0
.debug_frame 299840 299840 0 0.0
.debug_info 20194647 20194647 0 0.0
.debug_line 2649781 2649781 0 0.0
.debug_loc 2785870 2785870 0 0.0
.debug_ranges 280720 280720 0 0.0
.debug_str 3001804 3001804 0 0.0
.ramVecs 780 780 0 0.0
.resetVecs 64 64 0 0.0
.rodata 105585 105585 0 0.0
.shstrtab 232 232 0 0.0
.stab 204 204 0 0.0
.stabstr 441 441 0 0.0
.stack 2048 2048 0 0.0
.strtab 375840 375840 0 0.0
.symtab 255856 255856 0 0.0
.text 532524 532524 0 0.0

@Damian-Nordic Damian-Nordic merged commit a55b245 into project-chip:master Feb 9, 2023
@Damian-Nordic Damian-Nordic deleted the ext-address branch February 9, 2023 11:54
lpbeliveau-silabs pushed a commit to lpbeliveau-silabs/connectedhomeip that referenced this pull request Feb 13, 2023
15.4 drivers in Zephyr set EUI-64 as the link-layer address
of the corresponding interface. However, Hardware Address
field in the General Diagnostics cluster is supposed to
return Extended Address for Thread interfaces according to
the specification.

Make sure the diagnostic data provider returns the extended
address for the concerned field.

Signed-off-by: Damian Krolik <[email protected]>
lecndav pushed a commit to lecndav/connectedhomeip that referenced this pull request Mar 22, 2023
15.4 drivers in Zephyr set EUI-64 as the link-layer address
of the corresponding interface. However, Hardware Address
field in the General Diagnostics cluster is supposed to
return Extended Address for Thread interfaces according to
the specification.

Make sure the diagnostic data provider returns the extended
address for the concerned field.

Signed-off-by: Damian Krolik <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants